home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmrun.z
/
pmrun
Wrap
Text File
|
1998-10-20
|
7KB
|
133 lines
PPPPMMMMRRRRUUUUNNNN((((1111)))) PPPPMMMMRRRRUUUUNNNN((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmrrrruuuunnnn - graphical utility for entering PCP command line arguments
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////ppppccccpppp////bbbbiiiinnnn////ppppmmmmrrrruuuunnnn [----aaaa _a_r_c_h_i_v_e] [----hhhh _h_o_s_t] [----SSSS _s_t_a_r_t] [----TTTT _f_i_n_i_s_h] [----tttt
_d_e_l_t_a] [----xxxx _t_e_x_t] [----yyyy _t_e_x_t] _c_o_m_m_a_n_d [_s_p_e_c_i_f_i_c_a_t_i_o_n_s ...]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmrrrruuuunnnn is a configurable utility for launching applications within the
Performance Co-Pilot (PCP) framework. It is primarily a visual interface
to the more frequently used command line arguments for each tool, and is
intended as an aid in launching tools from the desktop.
ppppmmmmrrrruuuunnnn is based on the llllaaaauuuunnnncccchhhh(1) utility, and also understands a small set
of the common PCP command line arguments, and contains knowledge of the
semantics of these arguments. For example, the arguments for archives
(-a) and hosts (-h) are common to many of the PCP monitor tools, and are
also mutually exclusive arguments - this relationship is enforced by
ppppmmmmrrrruuuunnnn, while still allowing either type of metric source to be specified.
ppppmmmmrrrruuuunnnn must be run with a _c_o_m_m_a_n_d (must be an executable file) which is to
be executed when either the ``OK'' or ``Apply'' button is pressed.
The optional _s_p_e_c_i_f_i_c_a_t_i_o_n_s allow additional launch arguments to be
mapped to input fields for user completion. Again, this is intended to
provide a more obvious, self-explanatory interface to the launched
application than is provided by the command line.
The _o_p_t_i_o_n_s control the specific arguments which are presented to the
launched tool when either the ``OK'' or ``Apply'' button is pressed.
----aaaa Creates a finder widget which allows an archive filename to be
entered and subsequently passed to the launched tool via its own -a
argument. The default value presented in the finder will be
_a_r_c_h_i_v_e, which can be the empty string (_a_r_c_h_i_v_e is required if ppppmmmmrrrruuuunnnn
is given the -a argument, even if an empty string enclosed by quotes
is all that is used).
----hhhh Creates a finder widget which allows a hostname to be entered and
passed to the launched tool via its own -h argument. The default
value in the finder will be _h_o_s_t.
----SSSS Creates a text field which allows the _s_t_a_r_t time for metric fetches
from an archive to be entered. This field will not be editable if
both the -h and -a arguments have been presented to ppppmmmmrrrruuuunnnn and the
``Host'' toggle button is currently set. The times entered in this
text field validated according to the syntax rules described in
PPPPCCCCPPPPIIIInnnnttttrrrroooo(1) before being passed on to the launched tool.
----TTTT Similar to the -S argument, but allows the archive _f_i_n_i_s_h time to be
entered.
PPPPaaaaggggeeee 1111
PPPPMMMMRRRRUUUUNNNN((((1111)))) PPPPMMMMRRRRUUUUNNNN((((1111))))
----tttt Creates a text field and an associated time-units selection menu.
This allows the sample interval at which performance metrics will be
fetched from the metrics source to be specified. The interval
argument follows the syntax described in PPPPCCCCPPPPIIIInnnnttttrrrroooo(1), and in the
simplest form may be an unsigned integer (the implied units are
seconds). The default is 2.0 seconds.
----xxxx The _t_e_x_t following this argument will be prepended to the launched
_c_o_m_m_a_n_d before it is executed.
----yyyy The _t_e_x_t following this argument will be appended to the launched
_c_o_m_m_a_n_d before it is executed.
SSSSPPPPEEEECCCCIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN LLLLAAAANNNNGGGGUUUUAAAAGGGGEEEE
The language used to recognize the _s_p_e_c_i_f_i_c_a_t_i_o_n arguments to ppppmmmmrrrruuuunnnn is
designed to be simple and easily extended (programmatically) should the
need for different argument input mechanisms arise.
The general format for these arguments is a ``|'' separated string, with
the first argument distinguishing the user-interface element (type) which
is to be created. Currently the only supported specification type is for
text fields, and the remaining tokens are as follows:
_t_e_x_t|_f_l_a_g|_l_a_b_e_l|_d_e_f_a_u_l_t
The _t_e_x_t token identifies this as a text field. _f_l_a_g is the command line
flag to pass to the launched application (a ``-'' will be prepended to
this by ppppmmmmrrrruuuunnnn) when a value has been entered into this text field. _l_a_b_e_l
is the label associated with this text field, and _d_e_f_a_u_l_t is the string
displayed by default in the text field.
FFFFIIIILLLLEEEESSSS
////uuuusssseeee////lllliiiibbbb////XXXX11111111////aaaapppppppp----ddddeeeeffffaaaauuuullllttttssss////PPPPmmmmRRRRuuuunnnn
application resources
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ffffffffttttrrrr(1), iiiiccccoooonnnnbbbbooooooookkkk(1), llllaaaauuuunnnncccchhhh(1) and PPPPCCCCPPPPIIIInnnnttttrrrroooo(1).
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
All error conditions encountered will be reported via an error dialog,
and are intended to be self-explanatory.
PPPPaaaaggggeeee 2222